
<!DOCTYPE html>
<html class="client-nojs" lang="en" dir="ltr">
<head>
<meta charset="UTF-8"/>
<title>Autooptimiser - PanoTools.org Wiki</title>




<style media="screen" type="text/css" title="Screen style sheet"> @import url(manual.css); </style>

<meta name="generator" content="MediaWiki 1.35.3"/>
<meta name="viewport" content="width=device-width, initial-scale=1"/>





<!--[if lt IE 9]><![endif]-->
</head>
<body class="mediawiki ltr sitedir-ltr mw-hide-empty-elt ns-0 ns-subject page-Autooptimiser rootpage-Autooptimiser skin-vector action-view skin-vector-legacy">


<div id="content" class="mw-body" role="main">
	<a id="top"></a>
	
	
	<h1 id="firstHeading" class="firstHeading" lang="en">Autooptimiser</h1>
	<div id="bodyContent" class="mw-body-content">
		<div id="siteSub" class="noprint">From PanoTools.org Wiki</div>
		
		
		
		
		
		
		<div id="mw-content-text" lang="en" dir="ltr" class="mw-content-ltr"><div class="mw-parser-output"><p><b>autooptimiser</b> is a smart optimiser replacement for <a href="PTOptimizer.html" title="PTOptimizer">PTOptimizer</a> and <a href="Vig_optimize.html" title="Vig optimize">vig_optimize</a>, it is part of the <a href="Hugin.html" title="Hugin">hugin</a> suite of tools for panoramic imaging.
</p><p>It is not a 100% drop-in replacement for <b>PTOptimizer</b> as it has a slightly different interface and some extra features:
</p>
<ul><li><b>PTOptimizer</b> will write the output of the optimisation into the input script file as 'o' lines, deleting any that already exist.  This behaviour is a little strange, so <b>autooptimiser</b> writes the result to STDOUT or a new file, as is more usual for a command-line tool.</li>
<li>Not clobbering the original file means that there is no need to create 'o' lines, the output file is in the same format as the input with optimised values applied to the 'i' lines.</li>
<li><a href="PTStitcher.html" title="PTStitcher">PTStitcher</a> requires 'o' lines, so the output of <b>autooptimiser</b> isn't suitable for stitching with <b>PTStitcher</b> without further processing - Stitch these files with <a href="Nona.html" title="Nona">nona</a> instead.</li></ul>
<p>Additional features:
</p>
<ul><li><b>autooptimiser</b> can perform <i>pairwise</i> optimisation instead of trying to optimise all rotation parameters at the same time, this means that there is no need to pre-position images before optimisation.</li>
<li><i>levelling</i> the horizon in a set of images can be performed, this is the same functionality as the <b>Straighten</b> button in the <a href="Hugin_Preview_window.html" title="Hugin Preview window">hugin Preview window</a>.</li>
<li><i>auto-align</i> mode will pick an optimisation scheme suited to the distribution of <a href="Control_points.html" title="Control points">control points</a> in the project so there is no need to specify parameters to optimise.</li>
<li><b>autooptimiser</b> can adjust the panorama field of view<a class="external" href="https://wiki.panotools.org/Field_of_view">[*]</a>, dimensions and <a href="Projections.html" title="Projections">projection</a> to suit the input images.</li>
<li>the <b>field of view</b> of input images can be specified, this is useful as the project files created by <a href="Autopano.html" title="Autopano">autopano</a> and <a href="Autopano-sift.html" title="Autopano-sift">autopano-sift</a> don't specify the <b>field of view</b> of the input photos.</li>
<li><b>autooptimiser</b> can also perform photometric optimisation like the <a href="Vig_optimize.html" title="Vig optimize">vig_optimize</a> tool. Depending on the input images it selects automaticly these photometric parameters (exposure, white balance, <a href="Vignetting.html" title="Vignetting">vignetting</a>, <a href="Camera_response_curve.html" title="Camera response curve">camera response curve</a>) which should be optimised.</li></ul>
<h2><a name="Usage"><span class="mw-headline">Usage</span></a></h2>
<pre>      autooptimiser [options] project.pto
</pre>
<p>(- can be specified to read the project from stdio.)
</p>
<h3><a name="Description"><span class="mw-headline">Description</span></a></h3>
<p><b>autooptimiser</b> works similarly to <b>PToptimizer</b> but with extra command-
line options.
</p><p>It is also different in that PToptimizer appends its output onto the
input file in the form of ’o’ lines which need further processing.
autooptimiser simply updates the project and writes it to a new file.
</p>
<h3><a name="Options"><span class="mw-headline">Options</span></a></h3>
<p><tt>-o file.pto</tt> Output file. If omitted, stdout is used.
</p><p><br />
</p>
<ul><li>Optimisation options (if not specified, no optimisation takes place):</li></ul>
<p><tt>-a</tt>  Auto align mode, includes various optimisation stages, depending on
the amount and distribution of the control points
</p><p><tt>-p</tt>  Pairwise optimisation of yaw, pitch and roll, starting from first
image
</p><p><tt>-n</tt>  Optimize parameters specified in script file (like PToptimizer).
</p><p><tt>-m</tt>  Optimize photometric parameters (the optimized parameters are automatically selected depending on project settings)
</p><p><br />
</p>
<ul><li>Post-processing options:</li></ul>
<p><tt>-l</tt>  Level horizon (works best for horizontal panoramas)
</p><p><tt>-s</tt>  Automatically select a suitable output projection and size
</p>
<ul><li>Other options:</li></ul>
<p><tt>-q</tt>  Quiet operation (no progress is reported)
</p><p><tt>-v HFOV</tt>           Specify horizontal field of view of input images. Used if the .pto
file contains invalid HFOV values (autopano-SIFT writes .pto files
with invalid HFOV)
</p><p>When -a, -l, -s and -m options are used together, an operation similar to
the one of the "Align" button in hugin is performed.
</p>

<!--
Transclusion expansion time report (%,ms,calls,template)
100.00%    0.000      1 -total
-->


</div></div><div class="printfooter">Retrieved from "<a dir="ltr" href="https://wiki.panotools.org/index.php?title=Autooptimiser&amp;oldid=13134">https://wiki.panotools.org/index.php?title=Autooptimiser&amp;oldid=13134</a>"</div>
		</div></div></body></html>